Request-Uri
An example of the header is shown below:
sip:alice:secretword@atlanta.com;transport=tcp SIP/2.0 486 Busy Here
The header properties are shown in the following table:
|
Header Level Action |
Add |
Delete |
Modify |
List Entries |
|---|---|---|---|---|
|
Operations Supported |
No |
No |
Yes |
NA |
|
Keyword |
Sub Types |
Attributes |
|||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Method |
String |
Read/Write |
|||||||||||||||||||||||||||||||||||||||||||||
|
MethodType |
Enum:
|
Read/Write |
|||||||||||||||||||||||||||||||||||||||||||||
|
URI |
String |
Read/Write |
|||||||||||||||||||||||||||||||||||||||||||||
|
URL |
URL Structure (see URL) |
Read/Write |
Below are header manipulation examples:
|
Example 1 |
Rule: |
Test the Request-URI transport type. If 1 (TCP), then modify the URL portion of the From header: MessageManipulations 1 = 1, Invite.request, header.REQUEST-URI.url.user == '101', header.REMOTE-PARTY-ID.url, 2, 'sip:3200@110.18.5.41;tusunami=0', 0; |
|
Result: |
Remote-Party-ID: <sip:3200@110.18.5.41;tusunami=0>;party=calling;npi=0;ton=0 |
|
|
Example 2 |
Rule: |
If the method type is 5 (INVITE), then modify the Remote-Party-Id header: MessageManipulations 2 = 1, Invite.request, header.REQUEST-URI.methodtype == '5', header.REMOTE-PARTY-ID.url, 2, 'sip:3200@110.18.5.41;tusunami=0', 0; |
|
Result: |
Remote-Party-ID: <sip:3200@110.18.5.41;tusunami=0>;party=calling;npi=0;ton=0 |
|
|
Example 3 |
Rule: |
For all request URI's whose method types are 488, modify the message type to a 486: MessageManipulations 1 = 1, , header.request-uri.methodtype=='488', header.request-uri.methodtype, 2, '486', 0; |
|
Result: |
SIP/2.0 486 Busy Here |